edocs Home > BEA AquaLogic Data Services Platform 3.0/3.2 Documentation > ALDSP 3.2 New Features Documentation

Using Work Managers With ALDSP

This topic describes how to use Work Managers to prioritize the operation of dataspaces in AquaLogic Data Services Platform (ALDSP) 3.2.

Introduction

WebLogic Server prioritizes work and allocates threads based on administrator-defined parameters and actual run-time performance and throughput. Using Work Managers, you can configure scheduling guidelines and associate them with one or more applications, or with particular application components. This enables you to configure how an application prioritizes the execution of its work.

Using ALDSP 3.2, you can similarly use a Work Manager associated with a dataspace to specify scheduling guidelines. This enables you to configure the minimum or maximum number of threads allocated to a dataspace, for example. You could also define a Work Manager to specify the request class which enables you to  ensure that high priority work is scheduled before less important work, even if the lower priority work was submitted first.

Creating and Configuring Work Managers 

You can create a custom Work Manager for an ALDSP dataspace project using the WebLogic Server Administration Console. When creating a Work Manager, you must use the following format when assigning a name to the Work Manager:

wm/dataspace_name-default-workmanager where dataspace_name is the name of the ALDSP dataspace project

It is recommended that you create and configure a custom Work Manager before creating the associated dataspace project. If you create the dataspace project before creating the Work Manager, you will need to restart WebLogic Server to have the dataspace become associated with the custom Work Manager. You can then use the WebLogic Server Administration Console to modify the parameters of the Work Manager, as required.

WebLogic Server uses the global default Work Manager if a custom Work Manager does not exist. 

For more information about using WebLogic Server Administration Console to manage Work Managers and their associated constraints and request classes, see Using Work Managers to Optimize Scheduled Work

Sharing Work Manager Constraints

Multiple ALDSP dataspace projects cannot share the same Work Manager, but you can create two or more Work Managers that share the same underlying constraints. You might want to do this if you have two dataspace projects that need to access a particular JDBC connection pool, for example, and you want to prevent simultaneous access to the JDBC connection pool from exceeding the size of the pool.

To share Work Manager constraints in this case, do the following:

1.  Create a global max-threads-constraint associated with the JDBC connection pool.
2.  Create a separate Work Manager for each dataspace project associated with the max-threads-constraint.
3.  Create the dataspace projects (or restart WebLogic Server if the dataspace projects already exist).

See Also

How Tos

•   Using Work Managers to Optimize Scheduled Work